Skip to main content

This is a new service – your feedback will help us to improve it.

Newcastle-under-Lyme Borough Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

entity: 19206343

reference
T6-2\TPO0002_W4
name
tree-preservation-order

undefined

T6-2\TPO0002
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-2.268181 53.011766,-2.268296 53.011773,-2.268494 53.011780,-2.268727 53.011797,-2.268747 53.011685,-2.268786 53.011444,-2.268801 53.011363,-2.268826 53.011206,-2.268840 53.011134,-2.268838 53.011112,-2.268821 53.011082,-2.268806 53.011070,-2.268642 53.011026,-2.268613 53.011021,-2.268501 53.010989,-2.268389 53.010936,-2.268383 53.010922,-2.268377 53.010893,-2.268367 53.010865,-2.268346 53.010819,-2.268358 53.010797,-2.268364 53.010781,-2.268368 53.010756,-2.268366 53.010730,-2.268393 53.010621,-2.268394 53.010517,-2.268387 53.010453,-2.268380 53.010429,-2.268371 53.010413,-2.268359 53.010398,-2.268334 53.010374,-2.268234 53.010288,-2.268186 53.010250,-2.268086 53.010187,-2.267966 53.010115,-2.267768 53.010004,-2.267574 53.009910,-2.267535 53.009949,-2.267423 53.009997,-2.267391 53.010040,-2.267364 53.010123,-2.267320 53.010228,-2.267396 53.010441,-2.267495 53.010496,-2.267775 53.010647,-2.267796 53.010669,-2.267821 53.010699,-2.267827 53.010741,-2.267825 53.010858,-2.267846 53.010964,-2.267887 53.011049,-2.267905 53.011096,-2.267959 53.011266,-2.268007 53.011370,-2.268044 53.011457,-2.268066 53.011563,-2.268061 53.011669,-2.268052 53.011762,-2.268058 53.011761,-2.268181 53.011766)))
point
POINT (-2.268128 53.010886)
notes
entry-date
2026-07-28
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Newcastle-under-Lyme Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL